Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #4608
Obsolete
APIs for6.0.0
#4608For discussion
There are a couple of APIs left that are still marked as obsolete, which probably merit some discussion:
Extra
SentrySpan
,SentryTransaction
andTransactionTracer
all haveExtra
members like:sentry-dotnet/src/Sentry/SentrySpan.cs
Lines 82 to 84 in 748fcfe
sentry-dotnet/src/Sentry/SentrySpan.cs
Lines 86 to 88 in 748fcfe
Although we do probably want to get rid of these, as believe we also want to get rid of the
Data
members that we're recommending people switch to... since I think all of these will be replaced by Attributes at some stage right?Possibly we delay replacing these until the new Attributes are available and, at that point, we could ship an Analyzer and a Code fix to help people migrate (since Extras may be used quite widely).
GetInternalSentryOptions
We also have this, which is a bit of a misuse of the
ObsoleteAttribute
:sentry-dotnet/src/Sentry/SentryClientExtensions.cs
Lines 98 to 110 in 216bbc5
We could potentially replace it with this:
And then also ship a Roslyn Analyzer that warns if people use something decorated with
InternalApiAttribute
.CrashType
Same again for the APIs designed to deliberately create a crash:
sentry-dotnet/src/Sentry/CrashType.cs
Lines 7 to 8 in bd62cf0
EnableWatchdogTerminationTracking
Not sure what we want to do with this. Is the long term plan to remove this functionality entirely or are we planning to address the issues with this and "unobsolete" it eventually?
sentry-dotnet/src/Sentry/Platforms/Cocoa/SentryOptions.cs
Lines 147 to 157 in 4a608d4
In the meantime, do we want to remove it from the .NET API?